fix(deps): floor browserslist at 4.28.7 for today's advisories - #267
Open
ophiocus wants to merge 1 commit into
Open
fix(deps): floor browserslist at 4.28.7 for today's advisories#267ophiocus wants to merge 1 commit into
ophiocus wants to merge 1 commit into
Conversation
Two high advisories against browserslist <=4.28.6 landed today (GHSA-c83g-rgw3-j3cx, GHSA-73wf-gq98-2v4g — reached via the Docusaurus Babel chain, ~100 paths), so every pnpm verify run now fails its audit step repo-wide regardless of the change under test. Same override pattern as the existing floors in pnpm-workspace.yaml; the lockfile resolves to the patched 4.28.7. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #268.
Security/CI outage: two high
browserslistadvisories published today (~18:00Z) — GHSA-c83g-rgw3-j3cx, GHSA-73wf-gq98-2v4g, both covering<= 4.28.6— fail thepnpm auditstep of everyverifyrun repo-wide, so every open PR's next push goes red regardless of its content. Full analysis, evidence, and impact assessment in #268 (short version: build-time dep of the docs toolchain, so the urgency is the CI outage rather than a runtime surface).The patch: one floor in the existing
pnpm-workspace.yamloverrides pattern (same shape as thenanoidfloor already there); the lockfile resolves to the patched 4.28.7. Localpnpm verifyaudit step is clean with it.cc @adrian-lorenzo — small and urgent by nature; once this lands, the red
verifyon #245 (and any other PR that pushed since 18:00Z) clears on rebase/merge of main. Happy to adjust if you'd rather take it another way.